projects / cargo.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 4b5493c) | patch
Move test to a more appropriate location
authorCarol (Nichols || Goulding) <carol.nichols@gmail.com>
Sat, 19 Sep 2015 14:41:06 +0000 (10:41 -0400)
committerCarol (Nichols || Goulding) <carol.nichols@gmail.com>
Sun, 20 Sep 2015 03:30:37 +0000 (23:30 -0400)
commit05dc18029acd424949fb43645d228ca43ccc6a98
treee3489a41cde188f74468a5745f001b8c385b7245tree | snapshot
parent4b5493c2120699fe9bd6b695349b2d64a7593d87commit | diff
Move test to a more appropriate location

This test isn't testing generate-lockfile at all-- it's generating a
lockfile with `\r\n` in it in the test itself and then testing that
building will succeed even if there are `\r\n`s in the lockfile.

Given that generate-lockfile could change and have no effect on this
test, I think this fits in better with the other `cargo build` tests.
tests/test_cargo_compile.rs diff | blob | history
tests/test_cargo_generate_lockfile.rs diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.